7.1.1 Create MINPAY wallet payment order
#Brief description: MINPAY wallet scan code RMB recharge business interface. Users can complete the recharge of CNY to their wallet account by scanning the QR code.
- Request method: POST
- Request interface: https://gateway-domain/wallet-trade-merchant/v1/receive/internal/api/create
- Request media type (JSON data format)Content-Type: application/json
Request parameters
| Parameter name | Type | Required | Parameter meaning | Parameter description |
|---|---|---|---|---|
key | string | Yes | Merchant key | apiKey |
localOrderId | string | Yes | Merchant platform local order number | Merchant platform generates unique order number locally |
localUserId | string | No | Merchant platform local user ID | Merchant platform local user ID |
amount | number | Yes | Payment amount | Order amount |
notifyUrl | string | Yes | Callback address | After the order is successfully placed, the merchant's address will be notified by API callback | (For callback details, please refer to Document 3) |
successRedirectUrl | string | No | Address | Automatically jump to the address after success |
currency | string | Yes | Order currency | Order currency (wallet supported currency) |
expireSecond | Long | No | Expiration timestamp (seconds) | |
sign | string | Yes | Signature | See Signature Algorithm for details |
Request json sample
{
"key": "dNNTJZpgFVWlYrVv",
"localOrderId": "173322",
"notifyUrl": "http://127.0.0.1:8080/merchant-demo/notify",
"amount": 1,
"currency": "USDT",
"sign": "7f07092874886179997617567a98e20e"
}
Response json example
{
"code": 0,
"success": true,
"message": null,
"data": {
"orderId": "273719658252609",
"localUserId": null,
"localOrderId": "173322",
"orderType": "PAYMENT",
"orderBizType": "PAYMENT_WALLET_SCAN",
"paymentUrl": "https://walletapi.vapyapp.com/scan-pay/JJB7BvCtyxP3ieKk1pBpxnTposMtF4nvixsjdHCu7X8KEukfzB5h3bGa88Ke",
"publicKey": "JJB7BvCtyxP3ieKk1pBpxnTposMtF4nvixsjdHCu7X8KEukfzB5h3bGa88Ke"
}
}
The returned paymentUrl pops up the payment page, as shown below:
/7.1 MINPAY钱包扫码支付/wallet.jpg)
Response data parameter description
| Parameter name | Type | Parameter meaning | Parameter description |
|---|---|---|---|
orderId | string | Order ID | |
localUserId | string | Merchant ID | |
localOrderId | string | Merchant local order number | |
orderType | enum | Order Type | PAYMENT:支付订单 | WITHDRA:提款订单 |
orderBizType | enum | Order business | orderBizType type description is as follows |
paymentUrl | string | Address | Payment Address |
publicKey | string | Secret key | Public access key |
orderBizType type description:
- PAYMENT_WALLET_SCAN MINPAY wallet scan code payment
- PAYMENT_TRANSFER digital currency binding address direct deposit
- PAYMENT_ANY_DIGITAL_SCAN Scan the QR code to pay any amount of digital currency
- WITHDRAW_WALLET withdraw money to MINPAY wallet
- WITHDRAW_ANY_DIGITAL_WALLET Withdraw digital currency to any wallet
- PAYMENT_FIXED_DIGITAL_SCAN digital currency limited amount scan code payment
- BATCH_PAY batch payment
Callback returns json data
By default, all callback parameters participate in signature verification. For details of callback parameters, please see callback ]
Callback data
{
"amount": 11,
"bizType": "PAYMENT_FIXED_DIGITAL_SCAN",
"currency": "CNY",
"key": "h3cS7dBltRU4W1wD",
"localOrderId": "2820",
"merchantActualAmount": 8.86,
"merchantCurrency": "CNY",
"merchantId": 303122065665,
"merchantPaidAmount": 10.98,
"merchantUserId": "97",
"notifyTime": 1731572168370,
"orderCreateTime": 1731572133082,
"orderId": "273124814912907",
"sign": "699806308a9e055114c378671b0d2a15",
"status": "SUCCESS",
"type": "PAYMENT",
"userAmount": 1.55,
"userCurrency": "USDT"
}
When you receive the callback notification, please directly return the string success after the processing is completed, indicating that the message has been successfully received and processed. After the system receives the success response, it will no longer send the callback repeatedly. If the expected response is not received (success is not returned or an exception is returned), the system will resend the callback notification according to the stepped retry mechanism, retrying up to 14 times. The current retry intervals are: 15s, 15s, 30s,180s, 600s, 1200s, 1800s, 1800s, 1800s,3600s,10800s,10800s,21600s, 21600s